home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-05
/
21ripl.zip
/
README
< prev
next >
Wrap
Text File
|
1993-03-15
|
26KB
|
634 lines
REMOTE IPL SUPPORT FOR OS/2 2.1
INTRODUCTION
------------
OS/2 2.1 implements several system changes that require significant
changes to the LAN Server Remoteboot service. This document describes
how to install the LAN Server upgrades, how to update the Remote
IPL (RIPL) client definitions for different display types, and how
to support multiple versions of the OS/2 operating system in the
RIPL directory structure. Know problems are also described.
LAN Server 2.0 or LAN Server 3.0 with the OS/2 Remote IPL service
must already be installed before applying these updates. Updates
are provided for both LAN Server 2.0 and 3.0. The following files
are provided on the Remote IPL Service diskette:
- RPLMIG21.CMD Installation/migration procedure
- IBMLS.ZIP Updates common to LAN Server 2.0 and 3.0
- IBMLS20.ZIP Updates specific to LAN Server 2.0
- IBMLS30.ZIP Updates specific to LAN Server 3.0
- OS2.ZIP Special OS/2 2.1 utilities
VALID OS/2 / REMOTE IPL CONFIGURATIONS
--------------------------------------
The following table identifies valid OS/2 / Remote IPL configurations:
┌──────────┬───────────────────────────────────────────────────┐
│ Server │ Operating System to be RIPLed │
│ Operating│ 2.0+ │
│ System │ 1.3.2 2.0 Service Pak 2.00.1 2.1 │
├──────────┼──────────┼───────┼─────────────┼─────────┼────────┤
│ 1.3.2 │ Yes │ Yes │ Yes │ Yes │ Yes │
│ │ │ │ │ │ │
│ 2.x │ No │ Yes │ Yes │ Yes │ Yes │
└──────────┴──────────┴───────┴─────────────┴─────────┴────────┘
LAN SERVER REMOTE IPL SERVICE UPGRADES
--------------------------------------
The following changes/additions have been made to Remote IPL:
- A new rexx procedure, RPLMIG21.CMD, has been provided to install
the new Remote IPL support for OS/2 2.1.
- GETRPL.EXE and RPLUPINI.EXE (LAN Server 3.0 only) have been
updated to support the new INI file format implemented in OS/2 2.1.
- The Full Screen interface was updated to default the 'File Index
Table to model' parameter to DEFALT21.FIT when a OS/2 2.1 server
record is selected. Changes were also made to remove the 'Read'
attribute on OS/2 2.1 client INI files before attempting to
delete them. The client file AUTOEXEC.20 is updated to reflect
the boot drive id.
- The RPLSETD.CMD rexx procedure has been updated to support
OS/2 versions 2.0, 2.0 + Service Pak, 2.00.1 (Preload), and 2.1.
RPLSETD.CMD has been moved from the \IBMLAN\RPL directory to
the \IBMLAN\NETPROG directory. The old RPLSETD.CMD in the
RPL directory is renamed to RPLSETD.OLD.
- A new utility, RPLRXUTL.EXE, has been added to support the
new RPLSETD.CMD procedure.
- Default WINOS2 INI files are provided that are preconfigured
for VGA display support. XGA support statements are also
present but commented out.
KNOWN PROBLEMS
--------------
1. All RIPL clients will Trap E while booting. There is a simple
workaround. Before RIPLing any 2.1 clients rename the file
\IBMLAN\RPL\OS2.21\OS2\DLL\TCP.DLL to TCP.BAK.
This workaround does disable support for the touch displays. RIPL
clients will not be able to use the touch display support.
2. RIPL clients may also trap or hang when doing a Shutdown or
Ctrl+Alt+Del. However, if this occurs, the client should reboot
without problems after powering off an back on.
3. Medialess RIPL clients will Trap D if they attempt to access a
VDISK.
UPGRADING EXISTING REMOTE IPL SERVERS
-------------------------------------
To upgrade existing RIPL servers, use the following procedure:
1. Install Remote IPL upgrades. Refer to the section 'INSTALLING
NEW REMOTE IPL SERVERS' for information on installing the
upgrades.
2. Determine if the prior versions of OS/2 in the RIPL tree are
still required. If they are not required, delete the appropriate
OS2.20 or OS2.20a directory tree to recovery the hardfile space.
3. Use the OS/2 2.1 utility RIPLINST to install the OS/2 2.1 code.
Refer to the section 'OS/2 2.1 RIPLINST UTILITY' for additional
information.
4. Run the LAN Server utility GETRPL.EXE.
5. If the server will only be RIPLing OS/2 2.1 clients, use the
RPLSETD.CMD procedure to update the client DEFALT20 to support
OS/2 2.1. Refer to the section 'RPLSETD.CMD REXX PROCEDURE'
for information on RPLSETD.CMD.
If the server will be supporting prior versions of OS/2 in
addition to 2.1, refer to the section 'SUPPORTING MULTIPLE LEVELS
OF THE OS/2 OPERATING SYSTEM ' for details on how to support
multiple version of OS/2.
6. Use the RPLSETD.CMD procedure to update existing RIPL clients
that are to RIPL the OS/2 2.1 operating system.
7. If you have any customized workplace shell OS2 INI files, refer
to the section 'UPDATING MASTER WORKPLACE SHELL OS2.INI FILES'
for additional information.
8. Review the section 'CNVTINI.EXE UTILITY' concerning INI file
restrictions when supporting multiple OS/2 operating systems.
INSTALLING NEW REMOTE IPL SERVERS
---------------------------------
To install new RIPL servers, use the following procedure:
1. Install the LAN Server as described in the LAN Server documentation.
2. Follow the procedure described above for upgrading Remote IPL
servers.
3. If you plan to support multiple versions of OS/2 in the RIPL
tree, refer to the section 'SUPPORTING MULTIPLE LEVELS OF THE
OS/2 OPERATING SYSTEM ' for additional information.
INSTALLATION OF LAN SERVER REMOTE IPL UPGRADES
----------------------------------------------
The LAN Server Remote IPL upgrades are provided on a LAN Server Remote
IPL Service diskette. A rexx procedure, RPLMIG21.CMD, is provided
that will install the LAN Server upgrades. The upgrades can be installed
from the diskette or the upgrades can be copied to a hardfile and
installed from the hardfile.
The RPLMIG21.CMD procedure performs the following functions:
1. Creates new RIPL subdirectories to support OS/2 2.1.
2. Copies several master files from the RIPL OS/2 2.0 directories
into the new RIPL OS/2 2.1 directories.
3. Installs the LAN Server upgrade files to the appropriate
directories. RPLMIG21 will determine which version of LAN
Server is installed and copy the appropriate update files.
4. Upgrades the RPL.MAP file to add server records to
support OS/2 2.1.
5. Creates OS221*.CNF files to support the server records
created in step 4.
6. Update the server name references in the DEFALT21.FIT file
installed as part of step 3.
7. Update the master CONFIGRI.20 files to add the
DEVICE=Z:\OS2\TESTCFG.SYS statement required for OS/2 2.1
remote install.
Note: RPLMIG21.CMD creates a file called \IBMLAN\RPL\RPLMIG21.$$$
which is 'Read-only'. If RPLMIG21.CMD detects that this
file is already present, it will exit without installing
any updates. If for some reason you wish to rerun
RPLMIG21.CMD, you must first delete RPLMIG21.$$$. The
procedure RPLSETD.CMD will not execute if the RPLMIG21.$$$
file is not present.
To install from the diskette, do the following:
1. Insert the diskette in drive A.
2. At an OS/2 prompt, enter the following command
A:\RPLMIG21
To install from a hardfile, do the following:
1. Create a subdirectory, for example d:\RPLOS221.
2. Copy the files on the RIPL Service diskette to the
subdirectory created in step 1.
3. At a OS/2 prompt, enter the command:
d:\RPLOS221\RPLMIG21 /S:d:\RPLOS221
The /S parameter specifies the path to the directory
created in step 1.
The complete syntax for the RPLMIG21.CMD procedure is given below:
RPLMIG21.CMD [ ? | /h | /H] [/S:Sourcepath] [/L:Logfile]
where ? or /h or /H is a request for this help panel. If specified,
it must be first parameter.
/S:Sourcepath is the fully qualified path to the directory
which contains the files to be installed by RPLMIG21. The
default value is A:\.
/L:Logfile is the fully qualified name of a file to which all
messages and errors are to be logged. If Logfile is specified,
no messages or errors will be displayed on the screen.
OS/2 2.1 RIPLINST UTILITY
-------------------------
The RIPLINST utility used to install the OS/2 2.1 code for LAN Server
OS/2 Remote IPL is located (in packed format) on diskette 7 of the
OS/2 2.1 Installation diskettes. Refer to the LAN Server documentation
for information on installing and running the RIPLINST utility.
Previous versions of RIPLINST had a default target install directory of:
d:\IBMLAN\RPL\OS2.20 (OS/2 2.0)
or
d:\IBMLAN\RPL\OS2.20a (Service Pack)
(The drive letter d indicates the drive where OS/2 is installed.)
The RIPLINST for OS/2 2.1 has a new default target install directory. The
new default target install directory is:
d:\IBMLAN\RPL\OS2.21
This was done so that an existing ..\OS2.20 directory tree would not be
automatically overwritten. If you wish to upgrade an existing ..\OS2.20
directory tree, the target install directory must be updated before
starting the install process. The target directory must be on the same
drive where OS/2 Remote IPL was installed (this can be different from
where LAN Server is installed).
After using RIPLINST to install OS/2 2.1 for Remote IPL, the updated
version of the LAN Server utility, GETRPL.EXE, must be run. Refer to
the LAN Server documentation for information on running GETRPL.
RPLSETD.CMD REXX PROCEDURE
--------------------------
The RPLSETD.CMD procedure provides the following functions:
- Upgrade existing RIPL clients that use 16 bit display drivers
to use the new 32 bit VGA and XGA display drivers or the 16
bit 8514 driver provided in OS/2 2.00.1, 2.0 + Service Pak,
and 2.1.
- Can be used to change the display type (32 bit VGA/XGA or
16 bit 8514) that a RIPL client is using. RPLSETD does not
support converting from the new drivers back to the old 16
bit display drivers.
- Can be used to update a RIPL client to boot a different
version of OS/2 2.x. The OS/2 2.x code must be installed
in the RIPL directory structure. The following OS/2 2.x
versions conversions are supported:
old version new version
2.0 2.00.1
2.0+Service Pak
2.1
2.00.1 2.0+Service Pak
2.1
2.0+Service Pak 2.00.1
2.1
Note that there is no support for converting any of the newer
versions back to the original OS/2 2.0.
Client definitions can be updated individually or in a group (grouped by
display type and operating system).
The client name DEFALT20 is a special client name used by the OS/2
Remote IPL support as a default when creating a new client (not
modelling an existing client). If you are supporting prior versions
of OS/2 (i.e. 2.0, 2.00.1, or 2.0 + Service Pack) in the RIPL directory
tree, do not update DEFALT20 to support OS/2 2.1. You must leave
DEFALT20 at its current level to support the prior version(s) of OS/2.
To support OS/2 2.1 RIPL clients do the following:
- Create a 'new' RIPL client, for example, MODEL21, using the defaults.
- Use RPLSETD to update MODEL21 to support OS/2 2.1. Then use MODEL21
as a model client to create all future 2.1 clients.
- You may need to create multiple 2.1 models, one for each LAN type you
support.
If the only version of OS/2 that will be installed in the RIPL directory
tree is OS/2 2.1, you should update the client DEFALT20. Then all future
default clients will automatically support OS/2 2.1. Normally RPLSETD
only updates four client files and in some cases RPL.MAP; however,
DEFALT20, is a special case and ten files will be updated.
The syntax of RPLSETD.CMD is:
RPLSETD [/H] [/D:DISPLAY_DRIVER /C:CLIENT[,CLIENT2,CLIENT3,...] ]
[/O:CURRENT_OS2] [/N:NEW_OS2] [/L:LOGFILE] [/R:RESPONSE_FILE]
where:
/H
displays the syntax on screen. If specified, it must be the first
parameter.
/D:DISPLAY_DRIVER (DISPLAYDRIVER)
is the new display type for the client definition. The following
display types are valid:
IBMVGA32 32-bit VGA display driver
IBMXGA32 32-bit XGA display driver
IBM8514 16-bit 8514 display driver
/C:CLIENT[,CLIENT2,CLIENT3,...] (CLIENT or CLIENTLIST)
is the name of one or more OS/2 remote IPL client workstations
that are to be updated to support the specified display driver.
If multiple client names are specified, each client name must be
separated with a comma. Imbedded blanks are not allowed.
The response file keywords CLIENT and CLIENTLIST are equivalent
to each other. They may be specified as many times times as
necessary.
/O:CURRENT_OS2 (CURRENTOS2DIR)
is the root directory under \IBMLAN\RPL for the current version of
OS/2 2.0 that the client is using. This parameter is case sensitive.
The default is OS2.20. The /O and/or /N parameters should only be
specified when you need to switch a client from one OS version to
another OS version.
/N:NEW_OS2 (NEWOS2DIR)
is the root directory under \IBMLAN\RPL for the version of OS/2 2.0
that the client is to be switched to. This parameter is case
sensitive. The default is OS2.21. The /O and/or /N parameters
should only be specified when you need to switch a client from one
OS version to another OS version.
/L:LOGFILE (LOGFILE)
is the drive, path, and filename of a file to which all messages and
errors are to be logged. If this parameter is specified, the only
errors displayed on the screen will be for a failure to open the
logfile or for missing required parameters in the response file.
/R:RESPONSE_FILE
is the drive, path, and filename of a file that contains the command
inputs in keyword form (keyword=value). The valid keywords are
indicated above in () following each /X: syntax. Only one keyword
can be specified per line in the response file. The DISPLAYDRIVER,
CLIENT or CLIENTLIST, and LOGFILE parameters are required when using
a response file. If the /R parameter is specified, all other
parameters specified on the command line are ignored.
Since the new default target directory for OS/2 2.1 is ..\OS2.21, it will
be necessary to specify the parameter /N:OS2.21 on each invokation of
RPLSETD. The /O parameter only has to be specified if the user has used a
directory other than ..\OS2.20 to install previous version of the OS/2 2.0
code.
Examples:
- To update the DEFALT20 client to use the 32 bit VGA display driver
and switch the operating system from OS2.20 to OS2.21, type:
RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.21
This will update the default files to support OS/2 2.1 and the new
VGA display driver. These files are used when defining clients using
the default configuration.
Note: If you plan to also support previous versions of OS/2 (i.e.
2.0, 2.00.1, or 2.0 + Service Pak), do not update the DEFALT20
client.
- To update the MACH001 client to use the 32 bit XGA display driver
and switch the operating system from OS2.20 to OS2.21, type:
RPLSETD /D:IBMXGA32 /C:MACH001 /N:OS2.21
- To update the MACH001 client to use the 32 bit XGA display driver
and switch the operating system from OS2.20a to OS2.21, type:
RPLSETD /D:IBMXGA32 /C:MACH001 /O:OS2.20a /N:OS2.21
- To update multiple clients, MACH001 and MACH002, to use the 32 bit
VGA display driver and switch the operating system from OS2.20 to
OS2.21, type:
RPLSETD /D:IBMVGA32 /C:MACH001,MACH002 /N:OS2.21
- To use the response file option, do the following:
1. Create an ASCII file that contains the appropriate keyword
values. For example:
DISPLAYDRIVER=IBMVGA32
CLIENT=DEFALT20
CLIENT=MACH001,MACH002
CLIENTLIST=MACH003,MACH004
CURRENTOS2DIR=OS2.20
NEWOS2DIR=OS2.21
Note that CLIENT and CLIENTLIST are equivalent and that multiple
entries can be specified on either.
2. Type the following command:
RPLSETD /R:d:\path\response_filename
CREATING NEW OS/2 2.1 RIPL CLIENTS
----------------------------------
The menu interface has been updated to automatically select the
FITS\DEFALT21.FIT entry when a 'NEW' client is created using an
OS/2 2.1 server record id. However, the master CONFIG.20 files
have not been updated to OS/2 2.1 level so that back level versions
of OS/2 can also be supported.
The differences between an OS/2 2.0 and OS/2 2.1 CONFIG.20 file
are minor, mainly new SET statements. In most cases the CONFIG.20
file will work for OS/2 2.1 as is. However, if you wish to convert
the client CONFIG.20 to the OS/2 2.1 level, run the RPLSETD command
against the client. RPLSETD will update the CONFIG.20 file to the
OS/2 2.1 level.
A new client created using the defaults, will be configured to
support the IBMVGA32 display drivers. If the client has an XGA
or 8514 display attached, RPLSETD must be run against the client
to reconfigure the client for the correct display type.
UPDATING MASTER WORKPLACE SHELL OS2.INI FILES
---------------------------------------------
Some users have a master customized OS2.INI file that is copied to the
client directory each time the client is remote booted. This master file
must also be update to identify the type of display driver that the client
workstation is using. Clients with different display types (i.e. vga,
xga, 8514) MUST use different master OS2.INI files.
To update a master OS2.INI file, enter the following command:
RPLRXUTL /D:DISPLAY_DRIVER /C:INI_FILENAME
where:
/D:DISPLAY_DRIVER
is the same as for RPLSETD.
/C:INI_FILENAME
is the drive, path, and filename of the master OS2.INI file to be
updated.
For example:
RPLRXUTL /D:IBMVGA32 /C:E:\IBMLAN\RPL\MASTER\VGAOS2.INI
The RPLRXUTL utility will not display any error information. It does
return with a non-zero return code if there was an error. If you need
to verify error information, invoke RPLRXUTL from a CMD procedure (batch
file or Rexx) so that the return code can be tested.
WARNING: If the LAN Server is running on a OS/2 2.1 system, the format
of the INI file will be automatically converted to the new 2.1
format. If the INI file will be used by a RIPL client that
is booting a previous level of OS/2 (2.0, 2.00.1, or Service
Pak), a new OS/2 2.1 utility, CNVTINI.EXE, must be used to
convert the INI file back to the old format.
CNVTINI.EXE UTILITY
-------------------
The format of OS/2 INI files has been changed with the OS/2 2.1
operating system. This new format is incompatabile with previous
versions of OS/2. Old format INI files are automatically converted
to the new format by OS/2 2.1. However, in the RIPL environment,
there is a requirement to convert new format INI files back to the
old format (needed to support previous OS/2 versions on a RIPL server
that is running on OS/2 2.1). OS/2 2.1 provides a special utility,
CNVTINI.EXE, that converts a new format INI file to the old format.
This utility is temporarily being provided on the RIPL Support
diskette and is installed in the \IBMLAN\RPL\OS2.21\OS2 directory.
It is expected that in the final OS/2 2.1 product, this utility
will be shipped with OS/2 2.1.
If the RIPL server is running on a OS/2 2.1 system and the RPLRXUTL
utility is used to update the INI file of a RIPL client that will
be booting a previous level of OS/2, the CNVTINI utility MUST be
used to convert the updated INI file back to the old format.
To convert a new format INI file to the old format, enter the
command:
CNVTINI d:\path\INI_filename
where d:\path\INI_filename is the fully qualified name of the
INI file to be converted to the old
format.
Any utility program which uses the PRF API interface to open an INI
file under OS/2 2.1 will cause that INI file to be automatically
converted to the new format. Utilities which display the contents
of INI files will fall in this category. If a RIPL client booting
a previous version of OS/2 then tries to use that INI file, it will
fail because the format of the INI file is invalid. The CNVTINI
utility must be used to convert the INI file back to the old format
before it can be used by a previous level of OS/2.
SUPPORTING MULTIPLE LEVELS OF THE OS/2 OPERATING SYSTEM
-------------------------------------------------------
It is possible to install and support multiple levels of the OS/2
2.x operating system on a RIPL server. This section documents the
correct procedure to use to support such an environment. It is
assumned that the OS/2 2.1 Remote IPL Support updates have already
been installed.
The basic procedure is as follows:
1. Run the OS/2 utility RIPLINST to install the OS/2 code in
the RIPL directory tree. You must be carefully to use the
version of RIPLINST that matches the level of code to be
installed. RIPLINST is located on diskette 7 of all
OS/2 2.x installation diskettes. RIPLINST is unique for
each version of OS/2.
2. After running RIPLINST, run the LAN Server utility, GETRPL.
GETRPL uses information stored in the OS2SYS.INI file by
RIPLINST so it is very important that GETRPL be run
before using RIPLINST to install another version of OS/2.
3. Repeat steps 1 and 2 for each version of OS/2 that will be
RIPLed.
4. Determine whether the special RIPL client, DEFALT20, should
be updated by RPLSETD. This depends on what OS/2 versions
are installed.
OS/2 version 2.0 uses 16 bit display drivers. OS/2 versions
2.00.1, 2.0+Service Pak, and 2.1 use 32 bit display drivers
for VGA and XGA support. However, there are slight differences
in the XGA support between 2.00.1 and 2.0+Service Pak/2.1.
If OS/2 2.0 is present, DEFALT20 must not be updated. It
must remain as is to allow the creation of future 2.0 clients.
If OS/2 2.0 is not present, then DEFALT20 could be updated
with RPLSETD to support either 2.00.1 or 2.0+Service Pak/2.1.
To update DEFALT20 to support 2.0+Service Pack, enter the command:
RPLSETD /D:IBMVGA32 /C:DEFALT20
To update DEFALT20 to support 2.00.1, enter the command:
RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.20a
The /N parameter indicates that the new default target operating
system will be \IBMLAN\RPL\OS2.20a. The RIPLINST for OS/2 2.00.1
defaulted to a target directory of \IBMLAN\RPL\OS2.20a.
To update DEFALT20 to support 2.1, enter the command:
RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.21
The /N parameter indicates that the new default target operating
system will be \IBMLAN\RPL\OS2.21. The RIPLINST for OS/2 2.1
defaults to a target directory of \IBMLAN\RPL\OS2.21.
5. Since the special RIPL client DEFALT20 must be associated with
a specific OS/2 version, it is recommended that model clients
be created for the other OS/2 versions installed in the RIPL
tree. RPLSETD can be used to update the model client
definitions to point to the correct operating system. Then
these model clients can be used to create future clients for
each operating system type.